Low latency hybrid network for battery powered endpoint communications

ABSTRACT

Nodes included in a hybrid network establish cellular links infrequently and at staggered intervals. When a node establishes a cellular link, other nodes can transmit and receive data to a back office using that cellular link. In addition, the node can receive a request from the back office across the cellular link indicating that another node should respond to an on-demand read request. The node can then signal the other node via a wireless mesh network to establish a cellular link in order to respond to the on-demand read request. An advantage of the disclosed approach is that a battery powered node can communicate as often as needed with the back office without frequently establishing a cellular link and without maintaining a continuously active cellular link.

BACKGROUND OF THE INVENTION Field of the Invention

Embodiments of the present invention relate generally to wirelessnetwork communications and, more specifically, to a low latency hybridnetwork for battery powered endpoint communications.

Description of the Related Art

A conventional utility distribution infrastructure typically includesmultiple consumers, such as houses, business, and so forth, coupled to aset of intermediate distribution entities. The set of distributionentities draws resources from upstream providers and distributes theresources to the downstream consumers. In a modern utility distributioninfrastructure, the consumers as well as the intermediate distributionentities, may include Internet-of-Things (IoT) devices, such as smartutility meters and other network-capable hardware. These IoT devicesmeasure resource consumption to generate related metrology data. The IoTdevices periodically report the metrology data across the Internet orother network to a centralized management facility, often referred to asthe “back office.”

In many cases, the back office performs various management operationsfor the utility distribution infrastructure on behalf of one or morecustomers. A given customer could be, for example, a utility company oranother corporate entity that owns and/or operates all of or part of theutility distribution infrastructure. Typically, the back officeperiodically collects metrology data associated with the utilitydistribution infrastructure and provides that data to customers. Forexample, the back office could obtain metrology data from a set of IoTdevices every eight hours indicating utility consumption over aneight-hour interval. The back office also occasionally initiateson-demand read requests to read metrology data from one or more specificIoT device at the behest of the customer. For example, the customercould need a final utility meter reading from a particular smart utilitymeter located at a recently sold residence in order to prorate a utilitybill. The back office would transmit an on-demand read request to thatsmart meter to cause the smart meter to report the current meterreading.

Some types of IoT devices are designed to establish communication linksand connect to the Internet or other network via cellular modems thatcommunicate via a cellular network. For example, a given IoT devicecould be configured with a narrow-band IoT (NB-IoT) modem that couplesto a cellular network according to an NB-IoT protocol. The NB-IoT modemallows the given IoT device to establish a cellular link with a nearbycellular tower and then access the Internet or other network via thatcellular tower. One benefit of communicating over cellular links,especially those implemented via the NB-IoT protocol, is that IoTdevices can quickly connect to the Internet or other network. Anotherbenefit is that cellular links allow IoT devices to perform secure,Internet protocol (IP) based communications. For these reasons,customers oftentimes prefer that IoT devices communicate with the backoffice via cellular links instead of other communications channels.Among other things, cellular links allow IoT devices to report metrologydata more frequently and back offices to perform on-demand read requestswith IoT devices with relatively low latency.

One drawback of the above approach is that establishing and maintaininga cellular link typically consumes a good deal of power. Therefore,battery powered IoT devices cannot communicate via cellular linksfrequently without substantially reducing expected battery life.However, for a given IoT device to report metrology data regularly, inthe manner described above, the IoT device would need to establish acellular link quite often. Further, in order to permit the back officeto perform on-demand read requests with a given IoT device, the IoTdevice would need to maintain an active cellular link at all times.Battery powered IoT devices are usually designed with an expectedbattery life of at least 15 years; but establishing frequent cellularlinks and/or maintaining an active cellular link at all times can reduceexpected batter life to one year or less. When the depleted batteries ina battery powered IoT device need to be changed, a truck has to bedispatched, and a service person has to replace the depleted batteriesmanually, which can substantially increase operating overhead.

As the foregoing illustrates, what is needed in the art are moreeffective ways to communicate with battery powered devices within anetwork.

SUMMARY OF THE INVENTION

One embodiment of the present invention sets forth acomputer-implemented method for servicing read requests within a hybridnetwork, including receiving a first read request from a first servervia a first communication link, wherein the first communication linkcomprises a first type of communication link, determining that the firstread request is directed to a first node included in the hybrid network,generating a second communication link that couples the first node to asecond node also included in the hybrid network, wherein the secondcommunication link comprises a second type of communication link, andtransmitting the first read request to the first node via the secondcommunication link to allow the first node to service the first readrequest.

At least one technological advantage of the disclosed techniquesrelative to the prior art is that a battery powered node can communicatewith the back office as often as needed without having to establish acellular link frequently or having to maintain a continuously activecellular link. The battery powered node thus conserves battery power andcan operate for extended periods of time without needing replacementbatteries.

BRIEF DESCRIPTION OF THE DRAWINGS

So that the manner in which the above recited features of the presentinvention can be understood in detail, a more particular description ofthe invention, briefly summarized above, may be had by reference toembodiments, some of which are illustrated in the appended drawings. Itis to be noted, however, that the appended drawings illustrate onlytypical embodiments of this invention and are therefore not to beconsidered limiting of its scope, for the invention may admit to otherequally effective embodiments.

FIG. 1 illustrates a network system configured to implement one or moreaspects of the present invention;

FIG. 2A is a more detailed illustration of a node of FIG. 1, accordingto various embodiments of the present invention;

FIG. 2B is a more detailed illustration of the mesh interface of FIG.2A, according to various embodiments of the present invention;

FIG. 2C is a more detailed illustration of the computing device of FIG.2A, according to various embodiments of the present invention;

FIGS. 3A-3C illustrate how the nodes of FIG. 1 interoperate to transmitnetwork data across a given cellular link, according to variousembodiments of the present invention;

FIG. 4 is a flow diagram of method steps for causing a node to transmitnetwork data across a cellular link on behalf of one or more othernodes, according to various embodiments of the present invention;

FIGS. 5A-5C illustrate how the nodes of FIG. 1 interoperate to processan on-demand read request, according to various embodiments of thepresent invention; and

FIG. 6 is a flow diagram of method steps for causing a node to respondto an on-demand read request, according to various embodiments of thepresent invention.

DETAILED DESCRIPTION

In the following description, numerous specific details are set forth toprovide a more thorough understanding of the present invention. However,it will be apparent to one of skill in the art that the presentinvention may be practiced without one or more of these specificdetails. In other instances, well-known features have not been describedin order to avoid obscuring the present invention.

As discussed above, conventional battery powered IoT devices cannot beconfigured to communicate via cellular links very often withoutdrastically reducing expected battery life below acceptable levels. Inparticular, battery powered IoT devices cannot report metrology viacellular links as often as is needed without consuming excessive batterypower. In addition, battery powered IoT devices cannot respond toon-demand read requests via an active cellular link because maintainingan active cellular link consumes excessive battery power. Consumingexcessive battery power can reduce the operational lifetime of the IoTdevice from 15 years or more to one year or less. When the batteries inthe IoT device are depleted, a truck must be dispatched to replace thedepleted batteries, thereby increasing overhead and other operatingcosts.

To address these issues, embodiments of the invention include aplurality of low power or battery-powered nodes included in a hybridnetwork. The plurality of nodes establishes cellular links with acellular network only intermittently in order to conserve power. Theplurality of nodes establishes low power mesh links with one another toform a low power wireless mesh network. Each node can communicate simplecommand messages to other nodes included in the low power wireless meshnetwork with low latency and reduced power expenditure. The low powermesh links need not be secured when used to transmit simple commandmessages, thereby conserving power. Each node can also communicate, onan as-needed basis, with a back office that manages the hybrid networkacross a secure, IP-based cellular link.

Nodes included in the hybrid network establish cellular linksinfrequently and at staggered intervals. When a given node establishes acellular link, other nodes can transmit and receive data to the backoffice using that cellular link. In particular, the given node canaccumulate metrology data from the other nodes across the low powerwireless mesh network and then report this metrology data to the backoffice across the cellular network. In addition, the given node canreceive a request from the back office across the cellular linkindicating that another node should respond to an on-demand readrequest. The given node can then transmit a simple command message tothe other node via the wireless mesh network, causing the other node toestablish a cellular link for responding to the on-demand read request.

One technological advantage of the disclosed approach is that a batterypowered node can communicate as often as needed with the back officewithout establishing a cellular link very regularly or maintaining acontinuously active cellular link. The battery powered node thusconserves a great deal of battery power and therefore can operate forextended periods of time without needing replacement batteries. Becausethe disclosed approach reduces overhead while providing nodes with theability to communicate with the back office securely and with lowlatency, the disclosed approach represents multiple technologicaladvancements compared to prior art techniques.

System Overview

FIG. 1 illustrates a network system configured to implement one or moreaspects of the present invention. As shown, a network system 100includes a hybrid network 110, a carrier server 120, a mesh server 130,and an access point 140. Hybrid network 110 includes a plurality ofnodes 112 and a cellular tower 118. Each node 112 is configured toestablish a cellular link 114 to cellular tower 118, thereby forming acellular network 110(0) within hybrid network 110. Carrier server 120generally facilitates communications performed across cellular network110(0) via cellular tower 118. Each node 112 is also configured toestablish one or more mesh links 116 with one or more neighboring nodes112, thereby forming a mesh network 110(1) within hybrid network 110.Mesh server 130 generally coordinates mesh network 110(1) via accesspoint 140.

Nodes 112 can be powered by an external power source, such as a powergrid, powered by an internal power source, such as batteries, or solarpowered. As a general matter, though, nodes 112 operate with low powerand therefore perform specific operations to conserve power expenditure.A given node 112 can operate as a source node, an intermediate node, anda destination node. When operating as a source node, the given node 112generates and then transmits data across cellular network 110(0) and/ormesh network 110(1). When operating as an intermediate node, the givennode 112 receives data transmitted by a neighboring node via cellularnetwork 110(0) and/or mesh network 110(1) and then re-transmits the dataacross cellular network 110(0) and/or mesh network 110(1), Whenoperating as a destination node, the given node 112 receives datatransmitted across cellular network 110(0) and/or mesh network 110(1).

Nodes 112 operate according to a cellular communication protocol inorder to establish and maintain cellular links 114 with cellular tower118. In one embodiment, the cellular communication protocol may be thenarrow-band Internet-of-Things (NB-IoT) protocol. A given node 112establishes a cellular link using a cellular modem, as described belowin greater detail in conjunction with FIG. 2A. In so doing, the givennode 112 transmits identifying information included in a subscriberidentification module (SIM) card to carrier server 120 via cellulartower 118. In response, carrier server 120 authorizes the given node 112to establish a cellular link 114 with cellular tower 118. Carrier server120 then coordinates communications between the given node 112 and meshserver 130.

Nodes 112 implement a discovery protocol to identify and establish meshlinks 116 with one or more adjacent nodes. For example, node 112(1) mayimplement the discovery protocol to identify nodes 112(0), 112(2), and112(4) and establish communications with those nodes. When a given node112 discovers another node 112, those nodes exchange media accesscontrol (MAC) addresses and then schedule future communications with oneanother based on those MAC addresses. Mesh server 130 generallyconfigures each node 112 to implement the discovery protocol. Meshserver 130 also configures each node 112 with authentication credentialsthat allow nodes 112 to establish cellular links 114 and/or secure meshlinks 116 with one another. Mesh links 116 are generally wireless, radiofrequency (RF) communication links.

In one embodiment, nodes 112 may implement the discovery protocol todetermine the hopping sequences of adjacent nodes. The hopping sequenceof a node is the sequence of channels across which the node periodicallyreceives data. As is known in the art, a channel may correspond to aparticular range of frequencies. Once adjacency is established betweennodes 112, any of those nodes 112 can communicate with any of the othernodes 112 via one or more intermediate nodes 112 in the manner describedabove. Data communicated between nodes 112 may include an Internetprotocol (IP) packet, a short command message, metrology data, or anyother technically feasible unit of data. Any technically feasibleaddressing and forwarding techniques may be implemented to facilitatedelivery of the data from a source node to a destination node. Forexample, the data may include a header field configured to include adestination address, such as an IP address or media access control (MAC)address.

Each node 112 can be configured to forward received data based on adestination address. A given node 112 can also forward data based on aheader field that includes at least one switch label defining apredetermined path from a source node to a destination node. Nodes 112maintain a forwarding database that indicates which mesh link 116 shouldbe used and in what priority for transmitting data to a destinationnode. The forwarding database describes routes to a destination node andcost values associated with those routes. Any technically feasible typeof cost value can be implemented to characterize a link or a routewithin the mesh network 110(1).

In network system 100, access point 140 is configured to communicatewith at least one node within mesh network 110(1) and to alsocommunicate with mesh server 130 via network 142. Communication mayinclude transmission of payload data, timing data, authenticationcredentials, network configuration data, or any other technicallyrelevant data generated by mesh server 130 and destined for one or morenodes 112. Network 142 includes any technically feasible wired, optical,wireless, or hybrid network configured to transmit data between meshserver 130 and access point 140.

Mesh server 130 represents a destination for data generated by nodes112. Nodes 112 generally transmit this data to mesh server 130 viacellular network 110(0) for security and reduced latency. For example,nodes 112 could generate metrology data, such as electricity consumptiondata, and then transmit the metrology data to mesh server 130 acrosscellular links 114. Mesh server 130 can query nodes 112 to obtainvarious data in an on-demand manner. For example, mesh server 130 canissue on-demand read requests across cellular links 114 to cause nodes112 to report metrology data back to mesh server 130.

Nodes 112 establish cellular links 114 periodically and at differenttimes according to a communication schedule defined by mesh server 130.For example, each node 112 could be scheduled to establish a differentcellular link 114 at a different hour of any given day. Accordingly,under ordinary operating conditions, only one or only a subset ofcellular links 114 are active at any given time. Nodes 112 can establishand maintain mesh links 116 on an ongoing basis as needed to allow nodes112 to exchange data with one another at any time and with low latency.Nodes 112 can also activate mesh links 116 just prior to when a givennode 112 establishes a cellular link 114.

When reporting metrology data in the manner described above, nodes 112transmit the metrology data across mesh network 110(1) to a designatednode 112 that is scheduled to subsequently establish a cellular link114. The designated node 112 accumulates the metrology data from some orall other nodes 112 and establishes a cellular link 114 at the scheduledtime. The designated node 112 then transmits the accumulated metrologydata to mesh server 130 across the cellular link 114. Any given node 112that is scheduled to subsequently establish a cellular link 114 cansubsequently operate as the designated node. This approach is describedin greater detail below in conjunction with FIGS. 3A-4.

When a designated node 112 establishes a cellular link 114, that nodecan also receive on-demand read requests from mesh server 130 across thecellular link 114. Those on-remand read requests can target any of nodes112. The designated node 112 distributes on-demand read requests totargeted nodes 112 via mesh network 110(1). Upon receipt of an on-demandread-request, a receiving node 112 establishes a cellular link 114 toservice the on-demand read requests. In doing so, the receiving node 112may report up-to-date metrology data to mesh server 130. This approachis described in greater detail below in conjunction with FIGS. 5A-6.

As a general matter, nodes 112 included in hybrid network 110 performcommunications across both cellular network 110(0) and mesh network110(1) in the manner described in order to reduce the number of cellularlinks 114 that need to be established and maintained at any given time.Specifically, by sharing a single cellular link 114 established by onenode 112, the other nodes can avoid establishing a separate cellularlink 114. This approach reduces the energy that needs to be expended bynodes 112 when communicating with mesh server 130. Importantly, nodes112 that are powered by batteries advantageously implement thetechniques described herein to reduce energy consumption and extendbattery life. For example, under some conditions, a battery powered node112 that establishes a cellular link 114 only once per day can operatefor 15 years or more without needing replacement batteries. Accordingly,the disclosed techniques represent a significant technologicaladvancement over conventional approaches where battery powered nodesestablish and/or maintain separate cellular links, thereby consumingexcessive power.

The techniques described herein are sufficiently flexible to be utilizedwith any technically feasible combination of networks beyond cellularnetworks and mesh networks. For example, hybrid network 110 couldinclude a satellite network configured to facilitate globalcommunications with an elevated energy expenditure, as well as a localWiFi network configured to facilitate local communications with reducedenergy expenditure. As a general matter, hybrid network 110 can includeany two or more technically feasible networks across which nodes 112 cancommunicate.

FIG. 2A is a more detailed illustration of a node of FIG. 1, accordingto various embodiments of the present invention. As shown, node 112includes a mesh interface 200, a cellular interface 250, and a computingdevice 270, coupled together.

Mesh interface 200 is configured to establish one or more mesh links 116with one or more adjacent nodes 112. Mesh interface 200 generallyincludes one or more radio transceivers configured to transmit andreceive data packets. Mesh interface 200 can be configured to establishcommunications with adjacent nodes during the discovery processdiscussed above in conjunction with FIG. 1. FIG. 2B illustrate meshinterface 200 in greater detail.

Cellular interface 250 is configured to establish a cellular link 114with cellular tower 118 in order to allow node 112 to communicate withmesh server 130 via carrier server 120. Cellular interface 250 includesa SIM card (not shown) that includes authentication credentialsaccording to which carrier server 120 authenticates node 112 tocommunicate via cellular link 114. In one embodiment, cellular interface250 is an NB-IoT modem. In another embodiment, cellular interface 250 isconfigured to establish local communications with other cellularinterfaces 250 included in other nodes 112 in order to generate meshnetwork 110(1). In yet another embodiment, cellular interface 250 mayconsume an amount of power when generating and/or establishing a givencellular link 114 that is a multiple of the amount of power consumed bymesh interface 200 when generating and/or establishing a given mesh link116.

Computing device 270 coordinates the operation of mesh interface 200 andcellular interface 250. Computing device 270 also operates as a bridgebetween mesh interface 200 and cellular interface 250, thereby allowingdata that is received via one interface to be relayed across the otherinterface. When relaying data in this manner, computing device 270 canbuffer received data for subsequent transmission. Mesh server 130configures computing device 270 to implement any of the node operationsdiscussed herein, including executing scheduled communications viacellular link 114. For example, mesh server 130 could configurecomputing device 270 with a communication schedule according to whichcomputing device 270 would activate cellular interface 250 to establishcellular link 114.

As a general matter, computing device 270 causes mesh interface 200 togenerate and/or establish mesh links 116 more frequently, or with agreater periodicity, compared to how frequently computing device 270causes cellular interface 250 to generate and/or establish cellularlinks 114. For example, computing device 270 could cause mesh interface200 to generate a mesh link 116 with a periodicity of once per 8-hourinterval, and cause cellular interface 250 to generate a cellular link114 with a periodicity of once per 24-hour period. Either or both ofthese periodicities can be defined within the communication schedule. Inone embodiment, mesh server 130 generates the communication schedulebased on current battery depletion levels of nodes 112. An exemplarycomputing device that can implement computing device 270 is described ingreater detail below in conjunction with FIG. 2C.

FIG. 2B is a more detailed illustration of the mesh interface of FIG.2A, according to various embodiments of the present invention. Each node112 within the hybrid network 110 of FIG. 1 includes at least oneinstance of the network interface 200. The network interface 200 mayinclude, without limitation, a microprocessor unit (MPU) 210, a digitalsignal processor (DSP) 214, digital to analog converters (DACs) 220,221, analog to digital converters (ADCs) 222, 223, analog mixers 224,225, 226, 227, a phase shifter 232, an oscillator 230, a power amplifier(PA) 242, a low noise amplifier (LNA) 240, an antenna switch 244, and anantenna 246. Oscillator 230 may be coupled to a clock circuit (notshown) configured to maintain an estimate of the current time. MPU 210may be configured to update this time estimate, and other dataassociated with that time estimate, based on time synch beacons receivedfrom other nodes 112.

A memory 212 may be coupled to the MPU 210 for local program and datastorage. Similarly, a memory 216 may be coupled to the DSP 214 for localprogram and data storage. Memory 212 and/or memory 216 may be used tobuffer incoming data as well as store data structures such as, e.g., aforwarding database, and/or routing tables that include primary andsecondary path information, path cost values, and so forth.

In one embodiment, the MPU 210 implements procedures for processing IPpackets transmitted or received as payload data by mesh interface 200.The procedures for processing the IP packets may include, withoutlimitation, wireless routing, encryption, authentication, protocoltranslation, and routing between and among different wireless and wirednetwork ports. In one embodiment, MPU 210 implements the techniquesperformed by the node when MPU 210 executes a firmware program stored inmemory within network interface 200.

DSP 214 is coupled to DAC 220 and DAC 221. Each DAC 220, 221 isconfigured to convert a stream of outbound digital values into acorresponding analog signal. The outbound digital values are computed bythe signal processing procedures for modulating one or more channels.DSP 214 is also coupled to ADC 222 and ADC 223. Each ADC 222, 223 isconfigured to sample and quantize an analog signal to generate a streamof inbound digital values. The inbound digital values are processed bythe signal processing procedures to demodulate and extract payload datafrom the inbound digital values.

In one embodiment, MPU 210 and/or DSP 214 are configured to bufferincoming data within memory 212 and/or memory 216. The incoming data maybe buffered in any technically feasible format, including, for example,raw soft bits from individual channels, demodulated bits, raw ADCsamples, and so forth. MPU 210 and/or DSP 214 may buffer within memory212 and/or memory 216 any portion of data received across the set ofchannels from which antenna 246 receives data, including all such data.MPU 210 and/or DSP 214 may then perform various operations with thebuffered data, including demodulation operations, decoding operations,and so forth.

Persons having ordinary skill in the art will recognize that networkinterface 200 represents just one possible network interface that may beimplemented within nodes 112 shown in FIG. 1, and that any othertechnically feasible device for transmitting and receiving data may beincorporated within any of those nodes.

FIG. 2C is a more detailed illustration of the computing device of FIG.2A, according to various embodiments of the present invention. As shown,computing device 270 includes a processor 272, input/output (I/O)devices 274, and memory 276, coupled together.

Processor 272 includes any technically feasible set of hardware unitsconfigured to process data and execute software applications. Forexample, processor 272 could include one or more central processingunits (CPUs). I/O devices 274 include any technically feasible set ofdevices configured to perform input and/or output operations, including,for example, a universal serial bus (USB) port, among others. Memory 276includes any technically feasible storage media configured to store dataand software applications, such as, for example, a hard disk and/or arandom-access memory (RAM) module, among others. Memory 276 includes asoftware application 278. Software application 278 includes program codethat, when executed by processor 272, performs any of the node-orientedoperations discussed herein.

Aggregating Metrology Data for Transmission Across a Cellular Link

FIGS. 3A-3C illustrate how the nodes of FIG. 1 interoperate to transmitnetwork data across a given cellular link, according to variousembodiments of the present invention. As mentioned above in conjunctionwith FIG. 1, nodes 112 are configured to interoperate to share a singlecellular link 114 in order to reduce the number of cellular links 114that need to be established. Mesh server 130 configures nodes 112 toestablish cellular links 114 at different times according to acommunication schedule.

As shown in FIG. 3A, each of nodes 112 is associated with a differentcommunication time T0 through T5. A given node 112 establishes acellular link 114 at the corresponding communication time. Transmissiontimes T0-T5 may be evenly distributed across a 24-hour period ordistributed in any other technically feasible fashion. Nodes 112 areconfigured to analyze the communication schedule in order to determinewhen a subsequent transmission time occurs and which node 112 isdesignated to establish cellular link 114 at that time. Nodes 112 canthen transmit any metrology data to the designated node 112 forsubsequent transmission across cellular link 114, as described by way ofexample below in conjunction with FIG. 3B.

Referring now to FIG. 3B, node 112(0) accumulates metrology data 300from nodes 112(1)-112(5) prior to time T0. In one embodiment, nodes112(1)-112(5) transmit metrology data 300 within a threshold time spanof time T0. When time T0 arrives, node 112(0) establishes cellular link114 and then uploads bulk metrology data 310 across cellular link 114 tocarrier server 120. Bulk metrology data 310 could be, for example, acompressed form of accumulated metrology data 300. Carrier server 120provides this data to mesh server 130 or any third-party consumers ofsuch metrology data. Node 112(0) generally keeps cellular link 114active for a configurable amount of time, but typically limits that timeto prevent unnecessary energy expenditure. Another node 112 can performthe above process at a subsequent time, as described by way of examplebelow in conjunction with FIG. 3C.

Referring now to FIG. 3C, node 112(1) accumulates metrology data 320from nodes 112(1) and 112(2)-112(5) prior to time T1. When time T1arrives, node 112(1) establishes cellular link 114 and then uploads bulkmetrology data 330 across cellular link 114 to carrier server 120. Node112(1) subsequently terminates cellular link 114. According to thesetechniques, nodes 112 interoperate to generate communication pathwaysthat span hybrid network 110 and include both cellular links 114 andmesh links 116.

In one embodiment, the regularity with which any given node 112 needs toestablish a cellular link 114 may depend inversely on the number ofnodes 112 included in hybrid network 110. For example, with 24 nodes,each node 112 could establish a cellular link 114 once per 24-hourperiod. In this example, mesh server 130 would acquire metrology datafrom nodes 112 at one-hour intervals. However, increasing the number ofnodes to 48 would reduce the regularity with which each node needs toestablish a cellular link 114 to once per 48-hour period withoutchanging how often mesh server 130 acquires metrology data. In anotherembodiment, mesh server 130 configures nodes 112 to establish cellularlinks 114 with a regularity that is independent of how often the meshserver 130 needs to acquire bulk metrology data.

Under some circumstances, a given node 112 may be unable to establish acellular link 114. A neighboring node 112 can mitigate thesecircumstances by performing any scheduled communications on behalf ofthe given node 112. With any of the described techniques, nodes 112 cantransmit data to one another over unsecured mesh links 116, althoughnodes 112 can also establish secure IP-based mesh links 116 with oneanother in order to support the secure exchange of any sensitiveinformation.

As a general matter, the disclosed techniques advantageously scales inmanner that allows nodes 112 to communicate with mesh server 130 veryfrequently without needing any specific node 112 to frequently establisha cellular link 114. Accordingly, each node 112 can conserve a greatdeal of battery power and therefore operate for extended periods of timewithout needing replacement batteries. In addition, the disclosedtechniques can be adapted to provide metrology data to mesh server 130with any desired frequency without significantly impacting expectedbattery lifetime of nodes 112.

FIG. 4 is a flow diagram of method steps for causing a node to transmitnetwork data across a cellular link on behalf of one or more othernodes, according to various embodiments of the present invention.Although the method steps are described in conjunction with the systemsof FIGS. 1-3C, persons skilled in the art will understand that anysystem configured to perform the method steps, in any order, is withinthe scope of the present invention.

As shown, a method 400 begins at step 402, where a first node generatesmetrology data during a first time interval. The first node could be,for example, a smart meter configured to measure electricityconsumption. The first node is powered by batteries and thereforeperforms various techniques to conserve battery power. Mesh server 130configures the duration of the first time interval based on customerpreferences, among other possibilities.

At step 404, the first node analyzes a communication schedule todetermine that a second node is scheduled to communicate with meshserver 130 across a cellular link 114 at a first communication time, T0.The second node also performs step 404 to determine that the cellularlink 114 should be established at time T0. The second node may resideadjacent to the first node or across mesh network 110(1) by any numberof hops. Because mesh links 116 are low latency links, the first nodecan communicate with the second node via mesh network 110(1) with lowlatency without a significant dependency on the hop separation of thefirst and second nodes.

At step 406, the first node 112, determines that time T0 begins within athreshold time span. The first node 112 waits until time T0 beginswithin the threshold time span in order to maximize the amount ofmetrology data that can be collected and minimize the amount of time oneor more mesh links 116 between the first and second node need to beactive.

At step 408, the first node establishes a secure mesh link with thesecond node across mesh network 110(1). For example, the first nodecould establish IP-based communications with the second node via one ormore intermediate mesh links 116. In embodiments where the datagenerated at step 402 includes non-sensitive information, the first nodemay skip step 408.

At step 410, the first node transmits the metrology data generated atstep 402 to the second node to cause the second node to transmit themetrology data via the cellular link at time T0. Many other nodes 112can perform steps 402, 404, 406, 408, and 410 of the method 400 inconjunction with the first node in order to channel metrology data tothe second node, as well. In this manner, many nodes 112 can avoidneeding to establish a cellular link 114 by piggybacking communicationson the cellular link 114 established by the second node.

At step 412, the second node determines that time TO has arrived. Asmentioned, the second node also analyzes the communication schedule todetermine that the cellular link 114 should be established at time T0.At step 414, the second node stablishes the cellular link 114 at timeT0. In one embodiment, the second node initially establishes thecellular link 114 with carrier server 120 and then informs carrierserver 120 that the cellular link 114 may temporarily become inactive.This approach reduces the latency with which the cellular link 114 canbe reestablished. At step 416, the second node uploads the metrologydata that was collected from the first node via the cellular link 114.The second node can also upload metrology data collected by the secondnode and/or other metrology data collected by other nodes 112.

As a general matter, each node 112 included in hybrid network 110 isconfigured to perform the method 400. However, depending on variouscircumstances, any given node 112 may perform only a subset of the stepsof the method 400 at any given time. For example, when a given node 112is not scheduled to subsequently establish a cellular link 114, thegiven node 112 would perform steps 402, 404, 406, 408, and 410.Alternatively, when a given node 112 is scheduled to subsequentlyestablish a cellular link 114, the given node 112 would perform steps404, 412, 414, and 416.

Referring generally to FIGS. 3A-4, the disclosed approach permits nodes112 to provide metrology data to mesh server 130 over arbitrarily shortintervals without needing to frequently establish power-hungry cellularlinks individually. In practice, nodes 112 can be configured to reportmetrology data as frequently or as infrequently as desired independentlyof how often cellular links 114 are established. For example, adifferent node 112 could be configured to establish a cellular link 114at each different hour of a 24-hour period, though metrology data needonly be reported every six hours. This approach can further reduce powerconsumption. In various embodiments, a given node 112 can establish acellular link 114 outside of a scheduled communication time in responseto an alarm condition in order to report emergent situations to meshserver 130. Each node 112 can perform another technique in order toallow mesh server 130 to issue on-demand read requests to individualnodes 112, as described in greater detail below in conjunction withFIGS. 5A-6.

Leveraging a Wireless Mesh Network to Support On-Demand Read Access

FIGS. 5A-5C illustrate how the nodes of FIG. 1 interoperate to processan on-demand read request, according to various embodiments of thepresent invention. Under certain circumstances, mesh server 130 may needto read metrology data from an individual node 112 outside of the normalmetrology reporting intervals discussed above in conjunction with FIGS.3A-4. For example, mesh server 130 could need to determine a final meterreading at a residence that was recently sold in order to issue a finalutility bill to the seller of the residence. Nodes 112 implement thetechniques described below to service on-demand read requests.

As shown in FIG. 5A, node 112(5) establishes a cellular link 114 thatallows node 112(5) to communicate with mesh server 130 via carrierserver 120. Mesh server 130 transmits an on-demand read request 500 tonode 112(5) via cellular link 114. On-demand read request 500 can targetany node 112 included in hybrid network 110. In the example describedherein, on-demand read request targets node 112(0). On-demand readrequest 500 includes instructions indicating that node 112(0) shouldestablish a cellular link 114 to communicate with mesh server 130. Node112(5) processes on-demand read request 500 to identify node 112(0) andthen generates a short message 510 that includes instructions for node112(0). Short message 510 includes the MAC address of node 112(0) and a“call home” instruction.

As shown in FIG. 5B, node 112(5) transmits short message 510 across meshnetwork 110(1) to node 112(0) via intermediate nodes 112(3) and 112(2).Each intermediate node 112 parses short message 510 to extract the MACaddress portion, and then forwards short message 510 along anappropriate route to node 112(0) based on the MAC address. In practice,short message 510 need not be encrypted because short message 510 doesnot include sensitive data. Not encrypting short messages such as shortmessage 510 can reduce power consumption because establishing securemesh links 116 consumes additional power. Nonetheless, in variousembodiments, short messages can be transmitted in encrypted form asneeded. In some embodiments, nodes 112 simply forward on-demand readrequests to recipients instead of sending short messages 510.

As shown in FIG. 5C, upon receipt of short message 510, node 112(0)establishes a cellular link 114 and transmits metrology data 520 to meshserver 130 via cellular tower 118 and carrier server 120. Node 112(0)can then terminate cellular link 114. According to these techniques,nodes 112 interoperate to generate communication pathways that spanhybrid network 110 and include both cellular links 114 and mesh links116 for the purpose of servicing on-demand read requests.

In one embodiment, a given node 112 targeted by an on-demand readrequest may not be able to establish a cellular link 114 due tointerference or other factors. When such a situation occurs, the givennode 112 may cause another node 112 to service the on-demand readrequest on behalf of the given node 112. For example, node 112(0)described above could be unable to establish cellular link 114. Node112(0) could then send metrology data to node 112(5) to be uploadedacross the already-established cellular link 114.

As a general matter, the techniques described in conjunction with FIGS.5A-5C can be applied to cause nodes 112 to perform any technicallyfeasible operation beyond servicing on-demand read requests, as well.For example, mesh server 130 could transmit a firmware update to node112(5) when node 112(5) establishes cellular link 114. Node 112(5) couldthen distribute this firmware update across mesh network 110(0) to eachother node 112.

Importantly, these techniques allow nodes 112 to operate in a veryresponsive manner because mesh server 130 can communicate with anyspecific node 112 when any node 112 establishes a cellular link 114. Inaddition, this approach can be scaled to provide more frequent intervalsduring which mesh server 130 can communicate directly with specificnodes 112. For example, if mesh server 130 configures nodes 112 with acommunication schedule that causes nodes 112 to establish a cellularlink 114 at 20-minute intervals, then mesh server 130 could issueon-demand read requests to be serviced every 20 minutes, if needed.

FIG. 6 is a flow diagram of method steps for causing a node to respondto an on-demand read request, according to various embodiments of thepresent invention. Although the method steps are described inconjunction with the systems of FIGS. 1-5C, persons skilled in the artwill understand that any system configured to perform the method steps,in any order, is within the scope of the present invention.

As shown, a method 600 begins at step 602, where a first node analyzes acommunication schedule to determine that a first cellular link should beestablished with mesh server 130 at a first communication time, T0. Meshserver 130 generally configures nodes 112 to operate according to thesame communication schedule in order to permit those nodes to coordinatecommunications. The communication schedule includes a list of MACaddresses associated with nodes 112 and specific times or intervals wheneach corresponding node should establish a cellular link 114.

At step 604, the first node 112 establishes the first cellular link whentime T0 arrives. In one embodiment, the first node 112 establishes acellular link 114 when initially activated and then indicates to carrierserver 120 that the cellular link 114 may become temporarily inactive.This approach allows the first node 112 to deactivate the cellular link114 without carrier server 120 rescinding authorization for node 112 tore-activate that cellular link. Accordingly, when the firstcommunication time arrives, the first node 112 may be able to establishthe first cellular link very quickly.

At step 606, the first node receives instructions via the first cellularlink for a second node. The instructions could indicate, for example,that the second node should service an on-demand read request.Alternatively, the instructions could indicate that the second nodeshould perform any other technically feasible operation. In oneembodiment, if the second node fails to establish a cellular link 114 atthe scheduled time, then mesh server 130 may transmit instructions tothe first node indicating that the second node should service a statusupdate request.

At step 608, the first node transmits the instructions received at step606 across mesh network 110(1) to the second node. In one embodiment,the first node 112 may only establish one or more mesh links 116coupling the first node to the second node upon receipt of instructionsfor the second node. Any number of needed intermediate nodes 112 canforward the instructions across mesh network 110(1).

At step 610, the second node establishes a second cellular link based onthe instructions transmitted to the second node at step 608. Theinstructions typically include an on-demand read request indicating thatthe second node should establish a cellular link 114 to report metrologydata to mesh server 130. In response, at step 612, the second nodeestablishes the second cellular link and uploads metrology data to meshserver 130.

As a general matter, each node 112 included in hybrid network 110 isconfigured to perform the method 600. Depending on variouscircumstances, though, any given node 112 may perform only a subset ofthe steps of the method 600 at any given time. For example, when a givennode 112 is scheduled to subsequently establish a cellular link 114, thegiven node 112 would perform steps 602, 604, 606, and 608.Alternatively, when a given node 112 is not scheduled to subsequentlyestablish a cellular link 114, the given node 112 could perform steps610 and 612 in response to receiving instructions from another node.Advantageously, implementing the method 600 allows nodes 112 toestablish cellular links 114 sparingly yet still retain the ability tocommunicate with mesh server 130 in an on-demand manner and with verylow latency.

In sum, a plurality of nodes included in a hybrid network establishescellular links with a cellular network and establishes one or more meshlinks with a wireless mesh network. Each node can communicate with othernodes included in the hybrid network via low latency and low power meshlinks associated with the wireless mesh network. Each node can alsocommunicate with a back office that manages the hybrid network across asecure, IP-based cellular link.

Nodes included in the hybrid network establish cellular linksinfrequently and at staggered intervals. When a given node establishes acellular link, other nodes can transmit and receive data to the backoffice using that cellular link. In particular, the given nodeaccumulates metrology data from the other nodes across the wireless meshnetwork and then report this metrology data to the back office acrossthe cellular network. In addition, the given node can receive a requestfrom the back office across the cellular link indicating that anothernode should respond to an on-demand read request. The given node canthen signal the other node via the wireless mesh network to establish acellular link in order to respond to the in-demand read request acrossthe cellular network.

One technological advantage of the disclosed techniques relative to theprior art is that a battery powered node can communicate with the backoffice as often as needed without having to establish a cellular linkfrequently or having to maintain a continuously active cellular link.The battery powered node thus conserves battery power and can operatefor extended periods of time without needing replacement batteries. Inaddition, the disclosed techniques enable a battery powered node tocommunicate with the back office securely and with low latency. Thesetechnological advantages represent one or more technologicaladvancements relative to prior art approaches.

1. Some embodiments include a computer-implemented method for servicingread requests within a hybrid network, the method comprising receiving afirst read request from a first server via a first communication link,wherein the first communication link comprises a first type ofcommunication link, determining that the first read request is directedto a first node included in the hybrid network, generating a secondcommunication link that couples the first node to a second node alsoincluded in the hybrid network, wherein the second communication linkcomprises a second type of communication link, and transmitting thefirst read request to the first node via the second communication linkto allow the first node to service the first read request.

2. The computer-implemented method of clause 1, further comprising, inresponse to receiving the first read request, generating a thirdcommunication link that couples the first node to the first server,wherein the third communication link comprises the first type ofcommunication link.

3. The computer-implemented method of any of clauses 1-2, furthercomprising uploading metrology data associated with a current timeinterval to the first server via the third communication link to servicethe first read request.

4. The computer-implemented method of any of clauses 1-3, wherein thefirst node is unable to establish the first type of communication link,and further comprising transmitting metrology data associated with acurrent time interval to the second node via the second communicationlink, wherein the second node uploads the metrology data to the firstserver via the first communication link to service the first readrequest.

5. The computer-implemented method of any of clauses 1-4, whereingenerating the second communication link comprises establishing a firstmesh link with at least one adjacent node, wherein the at least oneadjacent node either comprises the first node or is coupled to the firstnode by one or more other mesh links.

6. The computer-implemented method of any of clauses 1-5, furthercomprising generating the first communication link at a firstcommunication time based on a schedule generated by the first server.

7. The computer-implemented method of any of clauses 1-6, wherein thefirst type of communication link comprises a cellular network link, andthe second type of communication link comprises a mesh network link.

8. The computer-implemented method of any of clauses 1-7, wherein thesecond node consumes a first amount of power over a first time intervalto generate the first communication link, and the second node consumes asecond amount of power over the first time interval to generate thesecond communication link, and wherein the first amount of power isgreater than the second amount of power.

9. The computer-implemented method of any of clauses 1-8, wherein thehybrid network includes a first network associated with the first typeof communication link and a second network associated with the secondtype of communication link.

10. The computer-implemented method of any of clauses 1-9, wherein eachof the first node and the second node comprises a low power node, abattery powered node, or a solar powered node.

11. Some embodiments include a non-transitory computer-readable mediumstoring program instructions that, when executed by a processor, causesthe processor to service read requests within a hybrid network byperforming the steps of receiving a first read request from a firstserver via a first communication link, wherein the first communicationlink comprises a first type of communication link, determining that thefirst read request is directed to a first node included in the hybridnetwork, generating a second communication link that couples the firstnode to a second node also included in the hybrid network, wherein thesecond communication link comprises a second type of communication link,and transmitting the first read request to the first node via the secondcommunication link to allow the first node to service the first readrequest.

12. The non-transitory computer-readable medium of clause 11, furthercomprising the steps of receiving metrology data associated with acurrent time interval from the first node via the second communicationlink, and uploading the metrology data to the first server via the firstcommunication link to service the first read request on behalf of thefirst node.

13. The non-transitory computer-readable medium of any of clauses 11-12,wherein the step of generating the second communication link comprisesestablishing a first mesh link with at least one adjacent node, whereinthe at least one adjacent node either comprises the first node or iscoupled to the first node by one or more other mesh links.

14. The non-transitory computer-readable medium of any of clauses 11-13,wherein the first type of communication link comprises a cellularnetwork link, and the second type of communication link comprises a meshnetwork link.

15. The non-transitory computer-readable medium of any of clauses 11-14,wherein the first type of communication link comprises a satellitenetwork link, and the second type of communication link comprises a WiFinetwork link.

16. The non-transitory computer-readable medium of any of clauses 11-15,wherein the second node consumes a first amount of power over a firsttime interval to generate the first communication link, and the secondnode consumes a second amount of power over the first time interval togenerate the second communication link, and wherein the first amount ofpower is greater than the second amount of power.

17. The non-transitory computer-readable medium of any of clauses 11-16,further comprising the step of generating the first communication linkto couple the second node to the first server via a second server,wherein the second server authorizes the second node to establish thefirst communication link.

18. The computer-implemented method of any of clauses 11-17, wherein thefirst server is coupled to a second server that relays communicationsbetween the first server and the second node.

19. Some embodiments include a system, comprising a first node thatresides in a hybrid network and generates first metrology data, and asecond node that resides in the hybrid network and performs the steps ofreceiving a first read request from a first server via a firstcommunication link, wherein the first communication link comprises afirst type of communication link, determining that the first readrequest is directed to the first node, generating a second communicationlink that couples the first node and the second node, wherein the secondcommunication link comprises a second type of communication link, andtransmitting the first read request to the first node via the secondcommunication link, wherein the first node services the first readrequest by uploading the first metrology data to the first server.

20. The system of clause 19, wherein the first type of communicationlink comprises a cellular network link, and the second type ofcommunication link comprises a mesh network link.

Any and all combinations of any of the claim elements recited in any ofthe claims and/or any elements described in this application, in anyfashion, fall within the contemplated scope of the present invention andprotection.

The descriptions of the various embodiments have been presented forpurposes of illustration, but are not intended to be exhaustive orlimited to the embodiments disclosed. Many modifications and variationswill be apparent to those of ordinary skill in the art without departingfrom the scope and spirit of the described embodiments.

Aspects of the present embodiments may be embodied as a system, methodor computer program product. Accordingly, aspects of the presentdisclosure may take the form of an entirely hardware embodiment, anentirely software embodiment (including firmware, resident software,micro-code, etc.) or an embodiment combining software and hardwareaspects that may all generally be referred to herein as a “module” or“system,” In addition, any hardware and/or software technique, process,function, component, engine, module, or system described in the presentdisclosure may be implemented as a circuit or set of circuits,Furthermore, aspects of the present disclosure may take the form of acomputer program product embodied in one or more computer readablemedium(s) having computer readable program code embodied thereon.

Any combination of one or more computer readable medium(s) may beutilized. The computer readable medium may be a computer readable signalmedium or a computer readable storage medium. A computer readablestorage medium may be, for example, but not limited to, an electronic,magnetic, optical, electromagnetic, infrared, or semiconductor system,apparatus, or device, or any suitable combination of the foregoing. Morespecific examples (a non-exhaustive list) of the computer readablestorage medium would include the following: an electrical connectionhaving one or more wires, a portable computer diskette, a hard disk, arandom access memory (RAM), a read-only memory (ROM), an erasableprogrammable read-only memory (EPROM or Flash memory), an optical fiber,a portable compact disc read-only memory (CD-ROM), an optical storagedevice, a magnetic storage device, or any suitable combination of theforegoing. In the context of this document, a computer readable storagemedium may be any tangible medium that can contain, or store a programfor use by or in connection with an instruction execution system,apparatus, or device.

Aspects of the present disclosure are described above with reference toflowchart illustrations and/or block diagrams of methods, apparatus(systems) and computer program products according to embodiments of thedisclosure. It will be understood that each block of the flowchartillustrations and/or block diagrams, and combinations of blocks in theflowchart illustrations and/or block diagrams, can be implemented bycomputer program instructions. These computer program instructions maybe provided to a processor of a general purpose computer, specialpurpose computer, or other programmable data processing apparatus toproduce a machine. The instructions, when executed via the processor ofthe computer or other programmable data processing apparatus, enable theimplementation of the functions/acts specified in the flowchart and/orblock diagram block or blocks. Such processors may be, withoutlimitation, general purpose processors, special-purpose processors,application-specific processors, or field-programmable gate arrays.

The flowchart and block diagrams in the figures illustrate thearchitecture, functionality, and operation of possible implementationsof systems, methods and computer program products according to variousembodiments of the present disclosure. In this regard, each block in theflowchart or block diagrams may represent a module, segment, or portionof code, which comprises one or more executable instructions forimplementing the specified logical function(s). It should also be notedthat, in some alternative implementations, the functions noted in theblock may occur out of the order noted in the figures. For example, twoblocks shown in succession may, in fact, be executed substantiallyconcurrently, or the blocks may sometimes be executed in the reverseorder, depending upon the functionality involved. It will also be notedthat each block of the block diagrams and/or flowchart illustration, andcombinations of blocks in the block diagrams and/or flowchartillustration, can be implemented by special purpose hardware-basedsystems that perform the specified functions or acts, or combinations ofspecial purpose hardware and computer instructions.

While the preceding is directed to embodiments of the presentdisclosure, other and further embodiments of the disclosure may bedevised without departing from the basic scope thereof, and the scopethereof is determined by the claims that follow.

1. A computer-implemented method for servicing read requests within ahybrid network, the method comprising: receiving, at a first nodeincluded in a plurality of nodes within the hybrid network, a first readrequest from a first server via a first communication link, wherein thefirst communication link comprises a first type of communication link,wherein each node included in the plurality of nodes is configured toestablish a separate communication link that comprises the first type ofcommunication link for communicating with the first server; determiningthat the first read request is directed to a second node included in theplurality of nodes hybrid; generating a second communication link thatcouples the first node to the second node, wherein the secondcommunication link comprises a second type of communication link; andtransmitting the first read request to the second node via the secondcommunication link to allow the second node to service the first readrequest.
 2. The computer-implemented method of claim 1, wherein, inresponse to receiving the first read request, the second node generatesa third communication link that couples the second node to the firstserver, wherein the third communication link comprises the first type ofcommunication link.
 3. The computer-implemented method of claim 2,wherein the second node uploads metrology data associated with a currenttime interval to the first server via the third communication link toservice the first read request.
 4. The computer-implemented method ofclaim 1, wherein the second node is unable to establish the first typeof communication link, wherein the second node transmits metrology dataassociated with a current time interval to the first node via the secondcommunication link, and wherein the first node uploads the metrologydata to the first server via the first communication link to service thefirst read request.
 5. The computer-implemented method of claim 1,wherein generating the second communication link comprises establishinga first mesh link with at least one adjacent node, wherein the at leastone adjacent node either comprises the second node or is coupled to thesecond node by one or more other mesh links.
 6. The computer-implementedmethod of claim 1, further comprising generating the first communicationlink at a first communication time based on a schedule generated by thefirst server.
 7. The computer-implemented method of claim 1, wherein thefirst type of communication link comprises a cellular network link, andthe second type of communication link comprises a mesh network link. 8.The computer-implemented method of claim 1, wherein the first nodeconsumes a first amount of power over a first time interval to generatethe first communication link, and the first node consumes a secondamount of power over the first time interval to generate the secondcommunication link, and wherein the first amount of power is greaterthan the second amount of power.
 9. The computer-implemented method ofclaim 1, wherein the hybrid network includes a first network associatedwith the first type of communication link and a second networkassociated with the second type of communication link.
 10. Thecomputer-implemented method of claim 1, wherein each of the first nodeand the second node comprises a low power node, a battery powered node,or a solar powered node.
 11. One or more non-transitorycomputer-readable media storing program instructions that, when executedby one or more processors, causes the one or more processors to serviceread requests within a hybrid network by performing the steps of:receiving, at a first node included in a plurality of nodes within thehybrid network, a first read request from a first server via a firstcommunication link, wherein the first communication link comprises afirst type of communication link, wherein each node included in theplurality of nodes is configured to establish a separate communicationlink that comprises the first type of communication link forcommunicating with the first server; determining that the first readrequest is directed to a second node included in the plurality of nodes;generating a second communication link that couples the first node tothe second node, wherein the second communication link comprises asecond type of communication link; and transmitting the first readrequest to the second node via the second communication link to allowthe second node to service the first read request.
 12. The one or morenon-transitory computer-readable media of claim 11, further comprisingthe steps of: receiving metrology data associated with a current timeinterval from the second node via the second communication link; anduploading the metrology data to the first server via the firstcommunication link to service the first read request on behalf of thesecond node.
 13. The one or more non-transitory computer-readable mediaof claim 11, wherein the step of generating the second communicationlink comprises establishing a first mesh link with at least one adjacentnode, wherein the at least one adjacent node either comprises the secondnode or is coupled to the second node by one or more other mesh links.14. The one or more non-transitory computer-readable media of claim 11,wherein the first type of communication link comprises a cellularnetwork link, and the second type of communication link comprises a meshnetwork link.
 15. The one or more non-transitory computer-readable mediaof claim 11, wherein the first type of communication link comprises asatellite network link, and the second type of communication linkcomprises a WiFi network link.
 16. The one or more non-transitorycomputer-readable media of claim 11, wherein the first node consumes afirst amount of power over a first time interval to generate the firstcommunication link, and the first node consumes a second amount of powerover the first time interval to generate the second communication link,and wherein the first amount of power is greater than the second amountof power.
 17. The one or more non-transitory computer-readable media ofclaim 11, further comprising the step of generating the firstcommunication link to couple the first node to the first server via asecond server, wherein the second server authorizes the first node toestablish the first communication link.
 18. The computer-implementedmethod of claim 1, wherein the first server is coupled to a secondserver that relays communications between the first server and the firstnode.
 19. A system, comprising: a first node included in a plurality ofnodes within a hybrid network and generates first metrology data,wherein each node included in the plurality of nodes is configured toestablish a separate communication link that comprises a first type ofcommunication link for communicating with a first server; and a secondnode included in the plurality of nodes that performs the steps of:receiving a first read request from the first server via a firstcommunication link, wherein the first communication link comprises thefirst type of communication link, determining that the first readrequest is directed to the first node, generating a second communicationlink that couples the first node and the second node, wherein the secondcommunication link comprises a second type of communication link, andtransmitting the first read request to the first node via the secondcommunication link, wherein the first node services the first readrequest by uploading the first metrology data to the first server. 20.The system of claim 19, wherein the first type of communication linkcomprises a cellular network link, and the second type of communicationlink comprises a mesh network link.